Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 554-tree-1
name: 1499
tree-preservation-order: undefined
554-tpo-1
uprn
address-text
point: POINT (-0.971827 50.866563)
geometry: MULTIPOLYGON (((-0.971770 50.866557,-0.971773 50.866568,-0.971780 50.866578,-0.971793 50.866586,-0.971809 50.866592,-0.971826 50.866594,-0.971844 50.866592,-0.971860 50.866587,-0.971872 50.866579,-0.971881 50.866569,-0.971884 50.866558,-0.971881 50.866547,-0.971873 50.866537,-0.971861 50.866529,-0.971845 50.866524,-0.971828 50.866522,-0.971810 50.866523,-0.971794 50.866528,-0.971781 50.866536,-0.971773 50.866546,-0.971770 50.866557)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL